Skip to main content

This is a new service – your feedback will help us to improve it.

Buckinghamshire Council

Tree preservation zone

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

The Chiltern District Council (Land adjacent to 5 and 7 Highover Park, Amersham, Buckinghamshire) Tr

reference
ZZZZDUESXE573
name
The Chiltern District Council (Land adjacent to 5 and 7 Highover Park, Amersham, Buckinghamshire) Tr
tree-preservation-order

undefined

TPO/1989/005
tree-preservation-zone-type
geometry
MULTIPOLYGON (((-0.604256 51.667625,-0.604246 51.667643,-0.604245 51.667657,-0.604248 51.667671,-0.604260 51.667683,-0.604279 51.667696,-0.604302 51.667706,-0.604316 51.667720,-0.604326 51.667736,-0.604332 51.667754,-0.604336 51.667780,-0.604348 51.667796,-0.604367 51.667804,-0.604385 51.667809,-0.604405 51.667810,-0.604425 51.667805,-0.604445 51.667797,-0.604466 51.667792,-0.604512 51.667794,-0.604532 51.667801,-0.604542 51.667814,-0.604549 51.667829,-0.604570 51.667840,-0.604592 51.667842,-0.604612 51.667841,-0.604636 51.667834,-0.604656 51.667824,-0.604673 51.667805,-0.604669 51.667782,-0.604653 51.667766,-0.604622 51.667755,-0.604578 51.667749,-0.604551 51.667738,-0.604536 51.667719,-0.604528 51.667706,-0.604518 51.667696,-0.604504 51.667688,-0.604468 51.667680,-0.604404 51.667678,-0.604390 51.667672,-0.604380 51.667662,-0.604383 51.667647,-0.604379 51.667632,-0.604339 51.667607,-0.604323 51.667605,-0.604304 51.667605,-0.604285 51.667608,-0.604273 51.667612,-0.604256 51.667625)))
point
POINT (-0.604442 51.667733)
notes
entry-date
2010-02-18
start-date
2010-02-18
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Buckinghamshire Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL